[feature] SC-166737/improve app proxy security by restricting where token replacements can go#51
Open
HappyPaul55 wants to merge 2 commits intomainfrom
Conversation
…oken replacements can go
|
Build for commit b3e22c3 deployed to: https://aircall-pr-51.ci.next.deskprodemo.com URLs: |
…oken replacements can go
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a configuration update to the
manifest.jsonfile, specifically enhancing how sensitive settings are injected into API requests. The main change is the addition of asettingsInjectionsection to better manage authorization headers for Aircall API credentials.Configuration improvements:
settingsInjectionblock to the API configuration, allowingaircall_api_idandaircall_api_tokento be injected into theAuthorizationheader for requests.